Foundry MCP Server

Created By
PraneshASPa year ago
A simple, lightweight and fast MCP server that provides Solidity development capabilities using the Foundry toolchain (Forge, Cast, and Anvil).
Overview

What is Foundry MCP Server?

Foundry MCP Server is a lightweight and fast Model Context Protocol (MCP) server that facilitates Solidity development using the Foundry toolchain, including Forge, Cast, and Anvil.

How to use Foundry MCP Server?

To use the server, install the Foundry tools, clone the repository, build the server, and configure your client (e.g., Claude desktop) to connect to it.

Key features of Foundry MCP Server?

  • Network interaction with local Anvil instances and remote RPC endpoints.
  • Contract interaction for reading and sending transactions.
  • Solidity development capabilities with a dedicated Forge workspace.
  • Utility functions for gas estimation, address computation, and more.

Use cases of Foundry MCP Server?

  1. Analyzing blockchain transactions.
  2. Deploying and managing Solidity contracts.
  3. Interacting with Ethereum nodes for data retrieval.

FAQ from Foundry MCP Server?

  • Is the Foundry MCP Server free to use?

Yes, it is open-source and free to use.

  • What are the system requirements?

You need Node.js v18+ and the Foundry toolchain installed.

  • Can I use it for mainnet transactions?

It is recommended to use it for testing and development purposes only.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PraneshASP
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago